env GOOS=target-OS GOARCH=target-architecture go build package-import-path
# Example
env GOOS=darwin GOARCH=amd64 go build
env GOOS=darwin GOARCH=amd64 go build main.go
env GOOS=darwin GOARCH=amd64 go build github.com/zoo/york/foo/bar| # vim style tmux config | |
| # use C-a, since it's on the home row and easier to hit than C-b | |
| set-option -g prefix C-a | |
| unbind-key C-a | |
| bind-key C-a send-prefix | |
| set -g base-index 1 | |
| # Easy config reload | |
| bind-key R source-file ~/.tmux.conf \; display-message "tmux.conf reloaded." |
| %% -*- erlang-indent-level: 4;indent-tabs-mode: nil -*- | |
| %% ex: ts=4 sw=4 et | |
| %% @author Kevin Smith <kevin@opscode.com> | |
| %% @copyright 2011 Opscode, Inc. | |
| -module(example). | |
| -behaviour(gen_server). | |
| -export([start_link/0]). |
A pattern for building personal knowledge bases using LLMs.
This is an idea file, it is designed to be copy pasted to your own LLM Agent (e.g. OpenAI Codex, Claude Code, OpenCode / Pi, or etc.). Its goal is to communicate the high level idea, but your agent will build out the specifics in collaboration with you.
Most people's experience with LLMs and documents looks like RAG: you upload a collection of files, the LLM retrieves relevant chunks at query time, and generates an answer. This works, but the LLM is rediscovering knowledge from scratch on every question. There's no accumulation. Ask a subtle question that requires synthesizing five documents, and the LLM has to find and piece together the relevant fragments every time. Nothing is built up. NotebookLM, ChatGPT file uploads, and most RAG systems work this way.
You are the middle manager for an autonomous software factory. You do NOT write code or implement issues yourself. Your job: read the issue tracker, fire off Devin coding sessions, ruthlessly keep them moving and honest, maximize the amount of correct, merged code — and keep me informed with only what needs my attention.
Single middle manager = you. You stay in control of the whole operation.
Your tools: you spawn and monitor coding sessions with your Devin session-creation / child-session tooling (choosing ultra or GPT-5.5-high per issue — policy in §4), read/write the board via the issue tracker's MCP, and reach humans via the Slack MCP. Operate continuously and autonomously — once you start, keep dispatching, monitoring, and unblocking; don't stop and wait for me unless you're genuinely blocked on a human decision (then use Slack and keep other plates spinning). I may be away for hours or days; maximize throughput the whole t
Helper script from docker.com
sudo sh <(curl -fsSL https://get.docker.com)
22 (SSH), 80 (HTTP), and 443 (HTTPS) to allow web traffic.WSA or Windows Subsystem for Android is a Tool that allows Windows to run Android Apps directly without using any emulator. The problem is Windows Subsystem for Android is currently only available through preview via the Beta Channel of the Windows Insider Program. But if you follow my guide, you don't have to be in Windows Insider Program to try it out. The only thing you need is Windows 11 installed and some patience.
WSA or Windows Subsystem for Android is a Tool that allows Windows to run Android Apps directly without using any emulator. The problem is Windows Subsystem for Android is currently only available through preview via the Beta Channel of the Windows Insider Program. But if you follow this guide, you don't have to be in Windows Insider Program to try it out. The only thing you need is Windows 11 installed and some patience.
| #!/usr/bin/env bash | |
| # git-worktree-helpers.sh | |
| # | |
| # Centralized git worktree management. | |
| # All worktrees live under: ~/.local/share/worktrees/<org>/<repo>/<branch> | |
| # derived automatically from the repo's origin remote. | |
| # | |
| # Functions: | |
| # wt <branch> [base] Create (or re-attach) a worktree for <branch> and cd into it. | |
| # New branches are based on [base] (default: HEAD). |